Sorry, forgot to mention that I have no custom panel to test, but the 2 lines of code are identical for each entrypoint.

Also, I assume there is no need to add it to the core.ts entrypoint as no UI elements go through there? And did I miss any edge points that I may not have thought to test?

Thanks for this PR! I'll dive into this tomorrow

This should also close #11034 which seems like a duplicate issue.

Any chance this can get in the upcoming Feb release? 🥺

Any chance this can get in the upcoming Feb release? 🥺

I don't think that is wise, I would like it to go through a complete beta and some testing before shipping this into production. We are not sure if this will break anything...

I don't think that is wise, I would like it to go through a complete beta and some testing before shipping this into production. We are not sure if this will break anything.

I understand the hesitation on a global setting, but...

• It's already broken! This is absolutely debilitating to any screen reader user. There is no work around. The mobile apps continue to be useless without this fix.
• The vast majority of components, including all mwc-* and nearly all paper-*, don't use the problematic module where this setting is employed. The only reason they are affected is because of reckless and intrusive coding IMHO. See the polymer issue I opened.
• The only documentation I could find on this setting is the single comment where it is declared, and that more or less acknowledges it is not needed and has detrimental effects:

* Setting to cancel synthetic click events fired by older mobile browsers. Modern browsers
 * no longer fire synthetic click events, and the cancellation behavior can interfere
 * when programmatically clicking on elements.
 */
export let cancelSyntheticClickEvents = true;

If you still think extensive testing is necessary, here are the only 9 modules in the entire source tree that actually import the offending gestures.js. It would not be difficult to quickly test where they are actually used in the frontend (if at all).

• node_modules/@polymer/iron-overlay-behavior/iron-overlay-manager.js:
  • 16: import * as gestures from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@polymer/paper-dropdown-menu/paper-dropdown-menu-light.js:
  • 27: import * as gestures from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@polymer/paper-dropdown-menu/paper-dropdown-menu.js:
  • 28: import * as gestures from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@polymer/paper-slider/paper-slider.js:
  • 21: import {setTouchAction} from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@polymer/polymer/lib/legacy/legacy-element-mixin.js:
  • 18: import { setTouchAction } from '../utils/gestures.js';
• node_modules/@polymer/polymer/lib/mixins/gesture-event-listeners.js:
  • 13: import { addListener, removeListener } from '../utils/gestures.js';
• node_modules/@vaadin/vaadin-button/src/vaadin-button.js:
  • 8: import { addListener } from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@vaadin/vaadin-date-picker/src/vaadin-date-picker-mixin.js:
  • 9: import { addListener } from '@polymer/polymer/lib/utils/gestures.js';
• node_modules/@vaadin/vaadin-date-picker/src/vaadin-date-picker-overlay-content.js:
  • 8: import { addListener, setTouchAction } from '@polymer/polymer/lib/utils/gestures.js';

I'm not worried about issues with current browsers but with the old browsers, like mentioned in that comment.

I'm not sure what devices/browsers are affected.

I guess we can put this in, as the beta generally doesn't find issues with old browsers anyway...

paper-dropdown-menu seems not to work anymore on iOS, I propose we revert this PR for now, and work on replacing all paper-dropdown-menu with mwc-select. After that we can enable this again (next release?).

In the meantime if needed, people could just stay on version 2022.2.0 until we have fixed this.